Skip to content

Add support for bird detection#7

Open
MikeFarrington wants to merge 1 commit intoKen98045:masterfrom
MikeFarrington:feature/AddBirds
Open

Add support for bird detection#7
MikeFarrington wants to merge 1 commit intoKen98045:masterfrom
MikeFarrington:feature/AddBirds

Conversation

@MikeFarrington
Copy link
Copy Markdown

Added support for "Bird" detection as its own category (not lumped into Animals).

@Ken98045
Copy link
Copy Markdown
Owner

Ken98045 commented Jan 12, 2021 via email

@MikeFarrington
Copy link
Copy Markdown
Author

MikeFarrington commented Jan 13, 2021

I think you misuderstand... I wasn't asking you to add support. I added support myself. It looks like I'm the first person to fork your code and work on it.

DeepStack does recognize birds. I didn't want to add it simply to "Animals", because in normal circumstances birds could be quite common and trigger false alarms. I have chickens and I want to make sure they don't escape their run.

You're able to view my changes and if you find them to be acceptable, you can merge them into your codebase.

image

@Ken98045
Copy link
Copy Markdown
Owner

Ken98045 commented Jan 13, 2021 via email

@Ken98045
Copy link
Copy Markdown
Owner

Ken98045 commented Jan 14, 2021 via email

@MikeFarrington
Copy link
Copy Markdown
Author

There's no conflicts, so this one can be easily merged by pressing the "Merge" button. I have a much larger commit that is a hefty cleanup of the folder structures. I'll that onto your changes, test it out, and submit a PR for that one as well.

@MikeFarrington
Copy link
Copy Markdown
Author

As far as your configuration settings, I was thinking about them going into the SQL database, but the registry works fine as well.

Speaking of that database... It'd be great to store the results from DeepStack as a 1:Many off of your tblMotionFiles. That way, you don't have to re-analyze as you navigate. I ran into a problem where I couldn't navigate while DeepStack was churning through a sizable backlog.

Would you object to my adding EntityFramework at some point? First though, I'd like to redo the installer in WiX Toolset. The Visual Studio Installer that is in use has long ago been deprecated. It's a dead technology.

I like to work around the periphery of a project and get to know it before I dive into the meat.

One last thing... You need to decide what open source / indemnification license model you wish to use, and place that into a LICENSE file in the root of the project. I probably shouldn't even be working on it, from a liability standpoint, until such a document is in place.

@Ken98045
Copy link
Copy Markdown
Owner

Ken98045 commented Jan 15, 2021 via email

@MikeFarrington
Copy link
Copy Markdown
Author

Yes, I too wanted to move things towards .NET Core if possible. Or .NET 5. .NET Core isn't really ready for WPF yet. I have plenty of WPF experience, but wasn't going to mention that just yet. :)

As for the registry, I suggest HKLM instead of HKCU. I don't think this is something will have multiple users on a system who want separate configurations. This plays a little into one of the first coding tasks I wanted to tackle... moving the file processing work out to a Windows Service so that the UI and Service are separate projects (sharing necessary code in a shared DLL).

This is the kind of program someone who is security conscious would want to run as a service using a dedicated and restricted service account instead of LocalSystem which is essentially admin.

Lastly, for the database MDF/LDF files, those really shouldn't be in Roaming. As that file grows, it'll make signing into and out of domain accounts slower as the files synchronize to the domain controller.

A good place for that is in C:\ProgramData\On-Guard. However, the installer would need to make that folder have modify privileges by default. Again however, that would only be if you want to move away from per-user installations which I think is wise in order to run as a service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants